-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
docs(core/dtos): improve by adding other usages #2167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 4.0
Are you sure you want to change the base?
docs(core/dtos): improve by adding other usages #2167
Conversation
e38ef0f
to
ecf50e4
Compare
4599bba
to
9b8f409
Compare
47e8434
to
b487437
Compare
b487437
to
9d49823
Compare
fix(dto): remove useless doc fix(operation): remove unused operation fix(typing): wrong return type fix(lint/md): bare url
9d49823
to
0bd7016
Compare
I struggled to find "simple ways" to deal with DTOs in APIP a few months back, so any additional info about it is really welcomed. Last time I checked, I wanted to created routes with basic filtering/sorting combined with DTO and I was surprised Doctrine Collection Provider wasn't mentioned as well. Maybe something to add? |
That's what I've tried to explain @soyuka and why I started with that #2167 (comment) (which now removed to fit with your review). |
Completes #2076.
Also fixes a coding style issue introduced by this commit e751b7e.